home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19990422-19990725
/
000305_news@columbia.edu _Tue Jul 20 10:25:13 1999.msg
< prev
next >
Wrap
Internet Message Format
|
1999-07-23
|
3KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id KAA07019
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 20 Jul 1999 10:25:12 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id KAA18411
for kermit.misc@watsun.cc.columbia.edu; Tue, 20 Jul 1999 10:04:41 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Subject: Re: set translation input command in Kermit 95?
Date: 20 Jul 1999 14:04:41 GMT
Organization: Columbia University
Message-ID: <7n1vlp$hv8$1@newsmaster.cc.columbia.edu>
To: kermit.misc@columbia.edu
In article <Pine.SUN.3.96.990720095136.21381A-100000@asterix>,
Rok Zevnik <zevnik@asterix.ijs.si> wrote:
: Maybe there's just another problem. That everything which runs on that
: host computer is made so that converts these characters in {}[]. And this
: is a lot of source to edit. So we have tomake changes on the client side.
:
You said earlier:
> On the host computer (RS/6000, AIX4.2) we have latin2-iso character set
> and the client (PC, Win95) is using CP1250.
>
And of course Kermit 95 fully supports this combination:
set terminal remote-character-set latin2
set terminal local-character-set cp1250
> But because the terminal which
> is connected on the host doesn't recognize the iso2 standart we are not
> allowed to use any of our native characters so we are running a script
> which converts that characters to '[]{}'. And we would like to see this
> characters to display correctly as =E8=E6=BE=F0 on our client.
>
So why don't you just remove the script?
What is the character set? Substitution of "national characters" for
"{}[]\|" is a method used in 7-bit ISO 646 character sets. We are aware
of only one such set for Eastern Europe, namely the Hungarian version of
ISO 646. Kermit 95 supports this set already with:
set terminal remote-character-set hungarian
Try that and see how it works.
If it doesn't interpret the {}[]\| characters properly for your language
(Slovenian?) then please send us the details of your character set.
: Maybe this solution would be useful if I set on client side that
: host computer uses cp437 and then with set key command translate outgoing
: characters in []{} but this is just half of the sollution because native
: signs will be printed alright but on display they won't see them.
:
There was a long discussion about this a few months ago, but unfortunately
I can't find the correspondence. The short answer is that SET TRANSLATION
INPUT was a very bad idea because it did not fit the ISO 2022 character-set
invocation and designation model. As you may know, Kermit can switch among
many character sets during a session based on escape sequences from the host.
In this setting, SET TRANSLATION INPUT makes no sense. Which character set
does it apply to? What is Kermit supposed to do when told to switch to
another character set?
- Frank